Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

Execute training notebooks for PRs

✓ INFO: Live previews are available —

• Open development series
• Open validation series

PR Summary

This PR introduces several functional updates and enhancements across deployment workflows, documentation templates, and notebooks. The key changes include:

1. Deployment Workflow Updates:

   • The S3 sync commands in the GitHub Actions workflows (for production, staging, and PR previews) have been updated to include a cache control header (--cache-control "no-cache, max-age=0, must-revalidate"). This change forces browsers and clients to fetch the latest content instead of using stale cached versions.

2. Template and Metadata Adjustments:

   • In the documentation template file, the generated-by footer timestamp has been updated to reflect a new generation date, ensuring documentation appears current.
   • The release listing file now includes an additional field (subtitle) in the list of fields, which may support richer metadata for release notes.

3. Notebook Modifications and Additions:

   • In one of the test configuration notebooks, the API endpoint parameters have been updated from a localhost development endpoint to a production URL. This reflects a transition from development to production settings.
   • A new notebook for a quickstart guide using the OIDC device flow has been added. This comprehensive notebook provides detailed instructions and code blocks for model documentation that authenticates via OIDC rather than using static API keys.

Overall, the changes aim to ensure that deployed documentation is not adversely affected by caching, that the documentation metadata remains up to date, and that users have access to contemporary authentication methods and detailed quickstart material for model documentation.

Test Suggestions

• Verify that the documentation sites on staging and production are updated immediately after deployment by checking the absence of cached content (e.g., by inspecting response headers for the cache-control directive).
• Run the GitHub Actions workflows manually or in a test branch to ensure the new cache control parameter does not interfere with file syncing or CloudFront invalidation.
• Execute the updated notebooks, particularly the new OIDC quickstart notebook, to confirm that all cells run as expected without errors and that the API endpoints are correctly reached.
• Review the release listing page to confirm that the additional 'subtitle' field is displayed and formatted properly.

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview